HTTP-based stream delivery

ABSTRACT

Stream delivery within a content delivery network (CDN) includes recording the stream using a recording tier, and playing the stream using a player tier. Recording begins when the stream is received in a source format. The stream is then converted into an intermediate format (IF), which comprises a stream manifest, one or more fragment indexes (FI), and a set of IF fragments. A player process begins when a requesting client is associated with a CDN HTTP proxy. In response to receipt at the proxy of a request for the stream, the HTTP proxy retrieves (either from the archive or the data store) the stream manifest and at least one fragment index. Using the fragment index, the IF fragments are retrieved to the HTTP proxy, converted to a target format, and then served in response to the client request. Preferably, fragments are accessed, cached and served by the proxy via HTTP.

BACKGROUND Technical Field

This application relates generally to delivery online of high definition(HD) video at broadcast audience scale to popular runtime environmentsand mobile devices.

Brief Description of the Related Art

Distributed computer systems are well-known in the prior art. One suchdistributed computer system is a “content delivery network” or “CDN”that is operated and managed by a service provider. The service providertypically provides the content delivery service on behalf of thirdparties. A “distributed system” of this type typically refers to acollection of autonomous computers linked by a network or networks,together with the software, systems, protocols and techniques designedto facilitate various services, such as content delivery or the supportof outsourced site infrastructure. Typically, “content delivery” meansthe storage, caching, or transmission of content, streaming media andapplications on behalf of content providers, including ancillarytechnologies used therewith including, without limitation, DNS queryhandling, provisioning, data monitoring and reporting, contenttargeting, personalization, and business intelligence.

While content delivery networks provide significant advantages,typically they include dedicated platforms to support delivery ofcontent for multiple third party runtime environments that are, in turn,based on their own proprietary technologies, media servers, andprotocols. These distinct platforms are costly to implement and tomaintain, especially globally and at scale as the number of end usersincreases. Moreover, at the same time, content providers (such aslarge-scale broadcasters, film distributors, and the like) desire theircontent to be delivered online in a manner that complements traditionalmediums such as broadcast TV (including high definition or “HD”television) and DVD. This content may also be provided at different bitrates. End users also desire to interact with the content as they can donow with traditional DVR-based content delivered over satellite orcable. A further complication is that Internet-based content delivery isno longer limited to fixed line environments such as the desktop, asmore and more end users now use mobile devices such as the Apple®iPhone® to receive and view content over mobile environments.

Thus, there is a need to provide an integrated content delivery networkplatform with the ability to deliver online content (such as HD-qualityvideo) at broadcast audience scale to the most popular runtimeenvironments (such as Adobe® Flash®, Microsoft® Silveright®, etc.) aswell as to mobile devices such as the iPhone to match what viewersexpect from traditional broadcast TV. The techniques disclosed hereinaddress this need.

BRIEF SUMMARY

An integrated HTTP-based delivery platform that provides for thedelivery online of HD-video and audio quality content to popular runtimeenvironments operating on multiple types of client devices in both fixedline and mobile environments.

In one embodiment, a method of delivering a live stream is implementedwithin a content delivery network (CDN) and includes the high levelfunctions of recording the stream using a recording tier, and playingthe stream using a player tier. The step of recording the streamincludes a set of sub-steps that begins when the stream is received at aCDN entry point in a source format. The stream is then converted into anintermediate format (IF), which is an internal format for delivering thestream within the CDN and comprises a stream manifest, a set of one ormore fragment indexes (FI), and a set of IF fragments. The fragmentsrepresenting a current portion of the stream are archived in theintermediate format in an archiver, while older (less current) portionsare sent to data store. The player process begins when a requestingclient is associated with a CDN HTTP proxy. In response to receipt atthe HTTP proxy of a request for the stream or a portion thereof, theHTTP proxy retrieves (either from the archive or the data store) thestream manifest and at least one fragment index. Using the fragmentindex, the IF fragments are retrieved to the HTTP proxy, converted to atarget format, and then served in response to the client request. Thesource format may be the same or different from the target format.Preferably, all fragments are accessed, cached and served by the HTTPproxy via HTTP.

In another embodiment, a method of delivering a stream on-demand (VOD)uses a translation tier to manage the creation and/or handling of the IFcomponents, i.e., the stream manifest, the fragment indexes (FI), andthe IF fragments. The translation tier is used in lieu of the recordingtier (in the live delivery network). In one VOD embodiment, thetranslation tier is implemented using an HTTP proxy and a translationprocess. The approach enables VOD streaming from customer and CDN-basedstorage origins, provides single and multiple bitrate (SBR and MBR)streaming, provides support for origin content stored in multipledifferent types of file format containers (supported mp4/flv codesinclude, among others, AAC, MP3, PCM for audio, and H.264 for video),and minimizes download of content beyond what is directly requested bythe end user.

According to another aspect of this disclosure, Intermediate Format (IF)generation and handling may occur entirely within an HTTP proxy. In thisapproach, IF can be extended throughout the entire downstream HTTPdelivery chain including, optionally, to the client itself (if theclient also has an HTTP proxy interface).

The foregoing has outlined some of the more pertinent features of thedisclosed subject matter. These features should be construed to bemerely illustrative. Many other beneficial results can be attained byapplying the disclosed subject matter in a different manner or bymodifying the subject matter as will be described.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed subject matter andthe advantages thereof, reference is now made to the followingdescriptions taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is a block diagram illustrating a known distributed computersystem configured as a content delivery network (CDN);

FIG. 2 is a representative CDN edge machine configuration;

FIG. 3 illustrates a network for HTTP-based delivery of high definition(HD) “live” video to clients across both fixed line and mobileenvironments according to the teachings of this disclosure;

FIG. 4 shows the network of FIG. 3 in additional detail;

FIG. 5 illustrates a representative packet flow across the network ofFIG. 3 from a source format (SF) to a target format (TF) using theIntermediate Fragments (IF) according to the disclosed technique;

FIG. 6 illustrates another view of the flow of media packets into andout of the streaming server framework;

FIG. 7 illustrates how the network for HTTP-based delivery is used toprovide video on demand (VOD) stream delivery; and

FIG. 8 illustrates a representative translation machine configuration ofthe VOD portion of the HTTP-based delivery network.

DETAILED DESCRIPTION

FIG. 1 illustrates a known distributed computer system that (asdescribed below) is extended by the techniques herein to provide asingle HTTP-based platform with the ability to deliver online HD videoat broadcast audience scale to the most popular runtime environments andto the latest devices in both fixed line and mobile environments.

In this representative embodiment, a distributed computer system 100 isconfigured as a content delivery network (CDN) and is assumed to have aset of machines 102 a-n distributed around the Internet. Typically, mostof the machines are servers located near the edge of the Internet, i.e.,at or adjacent end user access networks. A network operations commandcenter (NOCC) 104 may be used to administer and manage operations of thevarious machines in the system. Third party sites, such as web site 106,offload delivery of content (e.g., HTML, embedded page objects,streaming media, software downloads, and the like) to the distributedcomputer system 100 and, in particular, to “edge” servers. Typically,content providers offload their content delivery by aliasing (e.g., by aDNS CNAME) given content provider domains or sub-domains to domains thatare managed by the service provider's authoritative domain name service.End users that desire such content may be directed to the distributedcomputer system to obtain that content more reliably and efficiently.Although not shown in detail, the distributed computer system may alsoinclude other infrastructure, such as a distributed data collectionsystem 108 that collects usage and other data from the edge servers,aggregates that data across a region or set of regions, and passes thatdata to other back-end systems 110, 112, 114 and 116 to facilitatemonitoring, logging, alerts, billing, management and other operationaland administrative functions. Distributed network agents 118 monitor thenetwork as well as the server loads and provide network, traffic andload data to a DNS query handling mechanism 115, which is authoritativefor content domains being managed by the CDN. A distributed datatransport mechanism 120 may be used to distribute control information(e.g., metadata to manage content, to facilitate load balancing, and thelike) to the edge servers.

As illustrated in FIG. 2, a given machine 200 in the CDN (sometimesreferring to herein as an “edge machine”) comprises commodity hardware(e.g., an Intel Pentium processor) 202 running an operating systemkernel (such as Linux or variant) 204 that supports one or moreapplications 206 a-n. To facilitate content delivery services, forexample, given machines typically run a set of applications, such as anHTTP proxy 207, a name server 208, a local monitoring process 210, adistributed data collection process 212, and the like. The HTTP proxy207 typically comprises a cache, and a manager process for managing thecache and delivery of content from the edge machine. For streamingmedia, the machine typically includes one or more media servers, such asa Windows Media Server (WMS) or Flash 2.0 server, as required by thesupported media formats. When configured as a CDN “edge” machine (or“edge server”), the machine shown in FIG. 2 may be configured to provideone or more extended content delivery features, preferably on adomain-specific, customer-specific basis, preferably using configurationfiles that are distributed to the edge servers using a configurationsystem. A given configuration file preferably is XML-based and includesa set of content handling rules and directives that facilitate one ormore advanced content handling features. The configuration file may bedelivered to the CDN edge server via the data transport mechanism. U.S.Pat. No. 7,111,057 illustrates a useful infrastructure for deliveringand managing edge server content control information and this and otheredge server control information (sometimes referred to as “metadata”)can be provisioned by the CDN service provider itself, or (via anextranet or the like) the content provider customer who operates theorigin server.

The CDN may include a storage subsystem, such as described in U.S. Pat.No. 7,472,178, the disclosure of which is incorporated herein byreference.

The CDN may operate a server cache hierarchy to provide intermediatecaching of customer content; one such cache hierarchy subsystem isdescribed in U.S. Pat. No. 7,376,716, the disclosure of which isincorporated herein by reference.

For live streaming delivery, the CDN may include a live deliverysubsystem, such as described in U.S. Pat. No. 7,296,082, the disclosureof which is incorporated herein by reference.

As will be described, this disclosure describes how the above-identifiedtechnologies can be extended to provide an integrated HTTP-baseddelivery platform that provides for the delivery online of HD-videoquality content to the most popular runtime environments and to thelatest devices in both fixed line and mobile environments. The platformsupports delivery of both “live” and “on-demand” content.

Live Streaming Delivery

As used herein, the following terms shall have the followingrepresentative meanings. For convenience of illustration only, thedescription that follows (with respect to live streaming delivery) is inthe context of the Adobe Flash runtime environment, but this is not alimitation, as a similar type of solution may also be implemented forother runtime environments both fixed line and mobile (including,without limitation, Microsoft Silverlight, Apple iPhone, and others).

An Encoder is a customer-owned or managed machine which takes some rawlive video feed in some format (streaming, satellite, etc.) and deliversthe data to an Entry Point encoded for streaming delivery. An EntryPoint (EP) typically is a process running on a CDN streaming machinewhich receives video data from the customer's Encoder and makes thisdata available to consumers of the live stream. For Adobe Flash, this isa Flash Media Server (FMS) configured to accept connections fromEncoders. A Flash Media Server is a server process for Flash mediaavailable from Adobe Corporation. In this embodiment, an IntermediateRegion (IR) typically is a Flash Media Server which the CDN hasconfigured to act analogously to a streaming set reflector, such asdescribed in U.S. Pat. Nos. 7,296,082 and 6,751,673. These machinesrelay streams from FMS EPs to FMS Edge regions, providing fan out andpath diversity. A “Region” typically implies a set of machines (andtheir associated server processes) that are co-located and areinterconnected to one another for load sharing, typically over aback-end local area network. A Flash Edge machine is a Flash MediaServer which has been configured to accept client requests. This is thesoftware running on the Flash EP, IR, and Edge machines in arepresentative embodiment. Intermediate Format (IF) is an internal (tothe CDN) format for sending streaming data from EP to an edge serverHTTP proxy. As will be described in more detail below, IF preferablycomprises several different pieces, including “Stream Manifest,”“Fragment Indexes,” and “IF Fragments.” Live, DVR and VOD are defined asfollows: “Live” refers to media served in real time as an event occurs;“DVR” refers to serving content acquired from a “live” feed but servedat a later time; “VOD” refers to media served from a single, complete(i.e., not incrementally changing) file or set of files. Real TimeMessaging Protocol (RTMP) is the streaming and RPC protocol used byFlash. Real Time Messaging Protocol Encrypted (RTMPE) is the encryptedversion of RTMP using secrets built into the server and client. “SWF” or“Small Web Format” is the format for Flash client applications. SWFverification refers to a technique by which the Flash Player canauthenticate to FMS that it is playing an unmodified SWF by sendinghashes of the SWF itself along with secrets embedded in the client andserver.

FIG. 3 illustrates an overview of a preferred architecture for livestreaming delivery. A simplified version of this architecture is shownin FIG. 4. As can be seen in FIG. 3, the system generally is dividedinto two independent tiers: a stream recording tier 300, and a streamplayer tier 302. As will be described, the recording process (providedby the stream recording tier 300) is initiated from the Encoder 304forward. Preferably, streams are recorded even if there are currently noviewers (because there may be DVR requests later). The playback process(provided by the stream player tier 302) plays a given stream startingat a given time. Thus, a “live stream,” in effect, is equivalent to a“DVR stream” with a start time of “now.”

Referring to FIG. 3, the live streaming process begins with a streamdelivered from an Encoder 304 to an Entry Point 306. An RTMP Pullercomponent 308 (e.g., running on a Linux-based machine) in an EP Region(not shown) is instructed to subscribe to the stream on the EP 306 andto push the resulting data to one or more Archiver 310 processes,preferably running on other machines. As illustrated, one of theArchivers 310 may operate as the “leader” as a result of executing aleader election protocol across the archiving processes. Preferably, theArchivers 310 act as origin servers for the edge server HTTP proxyprocesses (one of which is shown at 312) for live or near-live requests.The edge server HTTP proxy 312 provides HTTP delivery to requesting enduser clients, one of which is the Client 314. A “Client” is a devicethat includes appropriate hardware and software to connect to theInternet, that speaks at least HTTP, and that includes a contentrendering engine. The Client device type will vary depending on whetherthe device connects to the Internet over a fixed line environment or amobile environment. A representative client is a computer that includesa browser, typically with native or plug-in support for media players,codecs, and the like. If DVR is enabled, content preferably is alsouploaded to the Storage subsystem 316, so that the Storage subsystemserves as the origin for DVR requests as will be described.

As also seen in FIG. 3, the content provider may choose to deliver twocopies of the stream, a primary copy, and a backup copy, to allow thestream to continue with minimal interruption in the event of network orother problems. Preferably, the primary and backup streams are treatedas independent throughout the system up through the edge server HTTPproxy, which preferably has the capability of failing over from theprimary to the backup when the primary is having difficulties, and viceversa.

A content request (from an end user Client 314) is directed to the CDNedge machine HTTP proxy 312, preferably using techniques such asdescribed in U.S. Pat. Nos. 6,108,703, 7,240,100, 7,293,093 and others.When an HTTP proxy 312 receives an HTTP request for a given stream, theHTTP proxy 312 makes various requests, preferably driven by HTTP proxymetadata (as described in U.S. Pat. Nos. 7,240,100, 7,111,057 andothers), possibly via a cache hierarchy 318 (see., e.g., U.S. Pat. No.7,376,716 and others) to learn about and download a stream to serve tothe Client 314. Preferably, the streaming-specific knowledge is handledby the edge machine HTTP proxy 312 directly connected to a Client 314.Any go-forward (cache miss) requests (issued from the HTTP proxy)preferably are standard HTTP requests. In one embodiment, the content isdelivered to the Client 314 from the HTTP proxy 312 as aprogressive-download FLV file. As noted above, the references herein toAdobe FLV are used herein by way of example, as the disclosedarchitecture is not limited for use with Adobe FLV. For secure streams,preferably the Client 314 first authenticates to the HTTP proxy 312using an edge server authentication technique and/or a SWF-verificationback-channel.

When a Client 314 requests a particular stream, the HTTP proxy 312 (towhich the client has been directed, typically via DNS) starts thestreaming process by retrieving a “Stream Manifest” that containspreferably only slowly changing attributes of the stream and informationneeded by the HTTP proxy to track down the actual stream content. TheURL to download this manifest preferably is constructeddeterministically from metadata delivered (e.g., via the distributeddata transport mechanism of FIG. 1) to the HTTP proxy. Preferably, themanifest itself is stored in association with a Stream Manifest Managersystem (not shown) and/or in the storage subsystem 316. Preferably, aStream Manifest describes the various “tracks” that compose a stream,where preferably each track constitutes a different combination of bitrate and type, where type is “audio,” “video,” or “interleaved_AV.” TheStream Manifest preferably includes a sequence of “indexlnfo” timeranges for each track that describe forward URL templates, streamproperties, and various other parameters necessary for the HTTP proxy torequest content for that time range.

For “live” requests, the HTTP proxy starts requesting content relativeto “now,” which, in general, is approximately equal to the time on theedge machine HTTP proxy process. Given a seek time, the HTTP proxydownloads a “Fragment Index” whose name preferably is computed based oninformation in the indexlnfo range and an epoch seek time. Preferably, aFragment Index covers a given time period (e.g., every few minutes). Byconsulting the Fragment Index, an “Intermediate Format (IF) Fragment”number and an offset into that fragment are obtained. The HTTP proxy canthen begin downloading the file (e.g., via the cache hierarchy 318, orfrom elsewhere within the CDN infrastructure), skipping data before thespecified offset, and then begin serving (to the requesting Client) fromthere. Preferably, the IF fragments are sized for optimal caching by theHTTP proxy. In general, and unless the Stream Manifest indicatesotherwise with a new indexlnfo range, for live streaming the HTTP proxythen continues serving data from consecutively-numbered IF Fragments.

As used herein, and in the context of live HTTP-based delivery, theIntermediate Format (IF) describes an internal representation of astream used to get data from the RTMP Puller through to the edge machineHTTP proxy. A “source” format (SF) is a format in which the Entry Point306 provides content and a “target” format (TF) is a format in whichedge machine HTTP proxy 312 delivers data to the Client 314. Accordingto this disclosure, these formats need not be the same. Thus, SF maydiffer from TF, i.e., a stream may be acquired in FLV format and servedin a dynamic or adaptive (variable bit rate) format. The format is thecontainer used to convey the stream; typically, the actual raw audio andvideo chunks are considered opaque data, although transcoding betweendifferent codecs may be implemented as well. By passing the formatsthrough the HTTP proxy (and delivering to the Client via conventionalHTTP), the container used to deliver the content can be changed as longas the underlying codecs are managed appropriately.

Referring now to FIG. 4, the HTTP streaming architecture for livecontent may work as follows. At step 1, a content provider's encoder 404pushes a live FLV stream to Entry Point (EP) 406. At step 2, the RTMPPuller 408 pulls the stream from the EP 406 and breaks it up intoIntermediate Format (IF) file fragments and corresponding indexinformation. A Demuxer process 405 facilitates this operation. ThePuller 408 preferably uses metadata from a Stream Manifest file todetermine how large to make each individual IF fragment. Preferably, andas noted above, IF fragment size is optimized for caching in the cacheassociated with an edge machine HTTP proxy.

At step 3, the Archiver 410 retrieves from the Puller 408 the IFfragments along with their corresponding index information. The Archiver410 appends the index information for each IF fragment to the currentFragment Index (FI) file. Preferably, the Archiver 410 caches apredetermined number of IF fragments for live play-back. As thefragments age out, preferably they are deleted from the Archiver 410and, at step 4, they are archived, e.g., to the Storage subsystem 416.Thus, at set intervals (e.g., every few minutes), the Archiver 410closes the current FI file, archives it to the Storage subsystem 416,and begins creating a new FI file.

At step 5, and after an end user Client 414 has been associated with aparticular edge machine, the HTTP proxy 412 in that machine gets thefragments for live play-back and limited DVR time periods from theArchiver 410 (possibly via the cache-hierarchy 418). Fragments no longeravailable on the Archiver 410 are retrieved from the Storage subsystem416. A Muxer process 415 that operates in association with the HTTPproxy 412 facilitates this operation. Preferably, each IF fragment is aseparate object for the HTTP proxy 412 that can be and is accessedthrough HTTP. In other words, according to this disclosure, the livestream is broken up into many small objects/fragments. The HTTP proxy412 receives DVR commands from the Client player, typically on aseparate HTTP connection. When the client player requests to beginplaying from a new stream position, the HTTP proxy uses metadata fromthe Stream Manifest file to calculate which FI file contains the targettime offset. The FI file is retrieved from the Archiver 410 or thestorage sub-system 416 (or, alternatively, from a peer machineco-located with the edge machine) and contains the IF fragment and byteoffset to begin streaming to the client player.

FIG. 5 illustrates a representative packet flow from source format (SF)to target format (TF), although the conversion processes may be omitted(in other words, source format bits may be placed in the IF Fragmentwithout additional format conversion). As noted above, preferably eachvideo stream is broken into Fragments. Fragments are numberedconsecutively starting at some arbitrary point (which can be determinedby consulting the Fragment Index). The sequence may be discontinuousacross Stream Manifest indexInfo ranges. Each Fragment preferablycomprises header information describing the type of data enclosed.Following these headers are the IF payload, such as a sequence of FLVtags. A target format may also be just an encrypted form (such as basedon AES128) of the elemental audio/video streams.

The Fragment Indexes enable the HTTP proxy process (to which aparticular Client has been associated) to find a frame around a desired“seek time.” Preferably, each Fragment Index file contains indexinformation covering a fixed amount of time. The exact interval isstored in the Stream Manifest for each indexInfo range. The desired seektime (epoch time) can be rounded down to the nearest interval boundaryto find the Fragment Index to request.

Preferably, each stream is represented completely by the StreamManifest, the Fragment Index and the IF Fragments. In an illustrativeembodiment, the Stream Manifest is an XML file that contains thefollowing information: stream epoch time (this time may be the time whenthe stream started or may be the oldest archived portion of the streamstill available); stream Properties (like bit rate, video size, codecinformation, etc.); information about fragment indexes and which URLpattern to use to request FI file; and URL pattern for the fragments.The Fragment Index (FI) typically comprises the following: informationabout which key frame to start streaming from for a given time slice;key frame-to-fragment number mapping, key frame-to-time mapping, keyframe to byte-offset in that fragment mapping, and so forth. Each IFFragment contains approximately N seconds of stream, preferablyoptimized for HTTP proxy caching and not necessarily fragmented on timeboundaries. Each fragment is composed of a fragment header, fragmentstream header and a payload, and each fragment is uniquely identified bythe fragment number. Fragment numbers incrementally increase.

Typically, and with reference back to FIG. 4, the Archiver 410 has thefragments for the most recent N minutes of the stream, and the rest ofthe fragments are on the Storage subsystem 416. The Archiver creates astream manifest XML file for each stream. It puts all the necessaryinformation that an HTTP proxy can use to make fragment and fragmentindex requests. For the Archiver to construct a Stream Manifest,preferably RTMP Puller sends the stream properties downstream.Preferably, the IF Fragment is used to serve time-related data, i.e.actual video/audio bytes. Also, preferably the HTTP proxy (to which theClient has been associated) makes requests for IF Fragments only. Thus,it is desirable to isolate fragments from packets that have streamproperties.

The Muxer subsystem 415 associated with (or within) the HTTP proxydetermines how to request IF, converts IF to the output stream, andpasses this data to the HTTP proxy for serving to the requesting client.In addition, preferably the HTTP proxy process supports a controlchannel by which the client can make any combination of various requestsagainst an active stream including, without limitation, sessionToken,seek, and switch. The control channel facilitates flow control whenworking in some runtime environments, such as where the client lacks itsown flow control facilities. In this situation, the control channelpasses throttle commands that may be based on a percentage of an averagebit rate (over the server-to-client connection) to help maintain full atarget buffer on the client side of the connection. A sessionTokenrequest is a request to provide additional authentication information,e.g., via SWF Authentication. A “seek” is a request to start sendingdata as of a different time in the stream (including “jump to live”). A“switch” is a request to start sending data from a different track fromthe same Stream Manifest. This might be a bit rate switch and/or anangle change.

Thus, the HTTP proxy receives DVR commands from the client player,preferably on a separate HTTP connection. When the client playerrequests that playback begin from a new stream position, the HTTP proxyuses metadata from the Stream Manifest file to calculate which FI filecontains the target time offset. The FI file is retrieved (e.g., fromthe Archiver or the Storage subsystem, or from a peer machine) andcontains the IF fragment and byte offset to begin streaming to theclient player.

As described, the Stream Manifest preferably is an XML file and containsinformation about fragment indexes and how to construct the URL for anFI file, how to construct the URL for the “now” request, and how toconstruct the URL for the fragments. The HTTP proxy caches the manifest,which can be retrieved to the proxy either from an Archiver (which maybe tried first), or the Storage subsystem. Client players connect to theHTTP proxy to play the live stream (i.e., connect to the stream's “now”time). In response, the HTTP proxy makes a forward request to theArchiver to fetch the “now” time on a live stream. Metadata in theStream Manifest is used by the HTTP proxy to create the “now” URL.

As also described, a stream has a number of FI files. Each containsstream keyframe information for a given time slice. The Fragment Indexallows time offsets to be mapped to fragment numbers and byte offsets.The Stream Manifest file defines the time slice for each FI file.

Each IF Fragment contains approximately N seconds of a stream. Eachfragment is composed of a header and a payload. The HTTP proxyunderstands the data in the header, but the payload is opaque. The HTTPproxy links together with a Muxer component to convert the IF-formattedpayload to the target format that is streamed to the client player. Thefragments are cached in the HTTP proxy for re-use, and each fragment isidentified with its stream name and an integer suffix that increasesincrementally. As described above, Archiver has the fragments for themost recent N minutes of the stream, and the rest of the fragments areon the Storage subsystem.

For non-authenticated content, preferably the client player connects toan http://URL to play a stream. Query string parameters can be used torequest a particular seek time if the default (live if the stream islive, or the beginning of the stream if it is not live) is notappropriate. For authenticated content, preferably the originalhttp://URL additionally contains a shared authentication token querystring parameter generated by the customer origin. This enables the HTTPproxy process to serve the stream for some configured amount of time(e.g. a given number of seconds). After that time, the HTTP proxyprocess terminates the connection unless, for example, an out-of-bandcontrol POST is received with a signed “session token.” Although notmeant to be limiting, in one approach this token preferably is generatedby the client by connecting to an FMS (or equivalent) edge machine thatcan perform SWF Verification (as shown in FIG. 3). The machine returnsthe signed session token to the client to be forwarded back to the HTTPproxy process as a control channel POST. Once the session token isreceived by the HTTP proxy, the stream preferably will playindefinitely. Other types of stream authentication may be implemented aswell.

FIG. 6 is another view of the flow of the media packets into and out ofthe streaming server framework of this disclosure for live streaming. Asnoted above, the framework processes (demuxes) the incoming mediapackets into an intermediate format (IF). In particular, the Encoderpushes the CDN customer content into an Entry Point. The Puller thenpulls the content from the EP and passes the data to its associatedDemuxer, which converts the incoming source format (SF, such as FLV) toIF fragments before injecting them into the Archiver network. AnArchiver receives data from the RTMP Puller and incrementally writesthis data to memory, such as a RAM disk (or other data store). If theHTTP proxy (to which a Client has been associated) requests a Fragmentor Fragment Index that is currently in the process of being receivedfrom the Puller, the Archiver sends the response (preferably in achunk-encoded HTTP response) so that the data can be sent as soon as itis received. Once a Fragment or Fragment Index is complete, a designatedleader Archiver (selected via a leader election process) attempts toupload the resulting file to the Storage subsystem. As noted above, themuxer component associated with the edge region/server processes (muxes)the packets to the desired target format (TF) before the packets reachthe end clients.

A Demuxer process may be integral to the Puller; likewise, a Muxerprocess may be integral to the HTTP proxy process. There may be oneDemuxer process for multiple Pullers; there may be one Muxer process formultiple HTTP proxies (within a particular Region).

As noted above, in terms of functionality, Demuxer converts regularstream packets into IF fragments and Muxer does the opposite. Bydefinition, Demuxer and Muxer should complement each other. As noted,Demuxer can be part of an RTMP Puller process or can be a separateprocess running on the RTMP Puller machine. Demuxer receives input viathe RTMP Puller. It is responsible to do the following: generate IFFragment Header, take the source format and package the same into IFbody, add Fragment Stream Header, Push IF fragment to Archiver, analyzethe fragment and generate index information pertinent to key framelocation within a given FLV packet, Push Key frame information to theArchiver. This can be done synchronously/asynchronously with respect tothe IF fragment transmission. Preferably, Demuxer also is responsiblefor determining an optimal size of the fragment, which fragment sizeshould be optimal for HTTP proxy caching. Demuxer can base its decision(regarding the optimal size of the fragment) by examining the followingstream properties: incoming live stream byte rate/bit rate; Key FrameInterval, or a combination of both. Apart from constructing IFFragments, Demuxer is also responsible to push Stream Properties and keyframe information to the Archiver. Archiver can then create the StreamManifest file that will be used by the HTTP proxy/Muxer to make fragmentindex and individual fragment requests. As described above, Muxercomplements Demuxer. As Demuxer is responsible for constructing IFFragments, Muxer is responsible for deconstructing the IF Fragments andconverting the IF Payload format to the target format (TF) that theClient requested. The Muxer may also provide the following informationto the HTTP proxy: statistics information about HTTP delivered Streams;and client session playback Information, such as playback duration,etc., and Muxer health data.

The Demuxer and Muxer enable dynamic transmux output to other fileformats. This enables the system to leverage a single set of contentsources for different device capabilities, e.g., iPhone 3.0 streamingusing MPEG-2 TS Segments, Microsoft Silverlight 3 (with H.264 playback),Shoutcast, and so forth.

As a variant to the above-described “pull” model that operates betweenan Encoder and an Archiver, it is also possible to use a “push-based”approach.

Video on Demand (VOD) Delivery

The above-described architecture is useful for live streaming,particularly over formats such as Flash. The following section describesadding video on demand (VOD) support to the platform. In particular, thesolution described below provides VOD streaming from customer andStorage subsystem-based origins, provides single and multiple bitrate(SBR and MBR) streaming, provides support for origin content stored inflv and mp4/flv containers (supported mp4/flv codes include, amongothers, AAC, MP3, PCM for audio, and H.264 for video), and minimizesdownload of content beyond what is directly requested by the end user.

For VOD delivery, the stream recorder tier 300 (of FIG. 3) is replaced,preferably with a translation tier, as will be described. For VODdelivery using HTTP, the Fragment Indexes may be generated from theorigin content on-the-fly (e.g., by scanning FLV or parsing MP4 MOOVatoms) and caching these indexes. Actual data retrievals may then beimplemented as “partial object caching” (POC) retrievals directly fromsource material at the edge region or via an intermediate translation(e.g., by a cache-h parent) into an Intermediate Format. As used herein,partial object caching refers to the ability of an HTTP proxy to fetch acontent object in fragments only as needed rather than downloading theentire content object. The HTTP proxy can cache these fragments forfuture use rather than having to release them after being served fromthe proxy. An origin server from which the content object fragments areretrieved in this manner must support the use of HTTP Range requests.

Before describing a VOD implementation in detail, the following sectiondescribes several ways in which VOD content is off-loaded for HTTPdelivery to the CDN. In a first embodiment, a conversion tool (a script)is used to convert source content flv to IF, with the resulting IF filesthen uploaded to the Storage subsystem. In this approach, metadata isused to have an HTTP proxy go forward to the Storage subsystem toretrieve the stream manifest, which then references the Storagesubsystem for the remaining content. In this approach, files in mp4/flvare first converted to flv (e.g., using ffmpeg copy mode) to change thecontainer to fly. Another approach is to have a CDN customer upload rawmedia files to the Storage subsystem and to run a conversion tool there.Yet another alternative is to have the customer (or encoder) producecontent in IF directly.

The translation tier approach is now described. In this approach, anon-demand dynamic IF generator machine takes requests for IF (manifests,indexes, and fragments) and satisfies these requests by dynamicallyretrieving flv or mp4/f4v input file ranges (either from the Storagesubsystem or customer origin). From there, HTTP proxy treatment isessentially the same as the “conversion tool” options described above.The generator machine preferably runs its own HTTP proxy (the“translator HTTP proxy”) to cache various inputs and outputs, togetherwith a translator process (described below) that accepts requests (e.g.,from a localhost connection to the translator HTTP proxy) and generatesIF based on data retrieved from the HTTP proxy via an associated cacheprocess. In an alternative, the translator process may comprise part ofthe translator HTTP proxy, in which case IF generation takes placewithin the proxy. Fragment generation may also be carried out in an edgemachine HTTP proxy or even further downstream (into the Client itself),such as where a Client maintains a session connection with one or morepeer clients.

An architecture and request flow of a preferred approach is shown inFIG. 7. In this embodiment, which is merely representative andnon-limiting, a translation tier 700 is located between an origin 702(e.g., customer origin, or the Storage subsystem, or both) and thestream player tier 704. In a representative embodiment, the translationtier executes in its own portion (e.g., a Microsoft IIS or equivalentnetwork) within the CDN, preferably in a Region dedicated to thispurpose. Alternatively, a translator (as described below) may run on asubset of HTTP-based edge machine Regions.

FIG. 8 illustrates a representative translator machine 800. Thismachine, like the machine shown in FIG. 2, includes CPU, memory, diskstore and network interfaces to provide an Internet-accessible machine.In addition, as shown in FIG. 8, in this embodiment, the two maincomponents of the translator machine comprise the HTTP proxy 802, and atranslator process 804. The HTTP proxy 802 performs partial objectcaching (POC) and interacts with the translator process 804, whichgenerates the stream manifest, index and fragments. The proxy andtranslator components interface to one another via shared memory 806 anda stream cache process 808, described in more detail below. Theoperation of the translation machine is best provided by way of anexample. The following section describes the request flow from client toorigin for a single bit rate (SBR) stream request, and how thecomponents described above facilitate this process. Example URLs areprovided.

As used below, “C” refers to the Client, “EG” refers to an edge machineHTTP proxy, “TG” refers to a translator machine HTTP proxy (such asproxy 802 in FIG. 8), “T” refers to the translator process (such asprocess 804 in FIG. 8), and “0” refers to origin (which may be acustomer origin or the CDN Storage subsystem).

C→EG:

The process begins when a Client makes a request to the edge machineHTTP proxy for the desired content. A representative URL might be asfollows:

URL: http://efvod.customer.com.akamaihd.net/foo/bar/baz.mp4

EG→itself:

The EG HTTP proxy then matches on the request pattern, and sets a numberof parameters, such as “event,” “angle,” “bitrate,” and “streamed.” Theactual pathname is the “event,” and the “streamid” identifies a customerconfiguration associated with the request.

EG→TG:

The EG HTTP proxy then goes forward to retrieve the Stream Manifest froma translator machine; preferably, the HTTP proxy goes forward byproviding a metadata-configured hostname (to the CDN DNS) that resolvesto addresses associated with the translator machines. Preferably, therequest path is prefixed with a customer identifier and protected by aper-customer secret, e.g., based on an authentication mechanism thatoperates between HTTP proxies. A representative URL might be as follows:

http://translator.customer.com.akamaihd.net/custid1/translate/foo/bar/baz.mp4?object=manifest

TG→T

If the translator HTTP proxy has already produced the Stream Manifest(or can find it, e.g., via ICP), the Manifest is returned to the edgeHTTP proxy that requested it. Otherwise, the translator HTTP proxyitself goes forward to localhost to retrieve the manifest. Preferably,the customer identifier prefix is preserved. The translator HTTP proxymay also apply one or more host headers on the manifest request (to thetranslator process) that are then echoed back to the translator HTTPproxy in any requests for origin content, metaindexes, etc. Preferably,all TG↔T interactions carry these same headers. These headers ensurethat the translator HTTP proxy is only fulfilling requests for theproper customer, and also to facilitate load balancing. The translatorrequests may also be authenticated using a cookie and a per-customersecret. A representative URL might be as follows:

http://translator.customer.com.akamaihd.net/custid1/translate/foo/bar/baz.mp4?object=manifestForward IP/port: 127.0.0.1:yyyy

T→TG:

The translator in turn retrieves the “metaindex” for the stream from thetranslator HTTP proxy using the stream cache process and the cookie. (Toproduce a manifest, typically only the beginning of the metaindex isretrieved.) The translator applies the customer-specific secret (fromthe original request) to the metaindex request back to the HTTP proxy.With the information in the “metaindex,” the translator produces theStream Manifest. A representative URL is as follows:

http://translator.customer.com.akamaihd.net/custid1/metaindex/foo/bar/baz.mp4&format=mp4

Forward IP/port: 127.0.0.1:80 TG→T:

If the translator HTTP proxy does not have the metaindex already cached,it again goes forward to the translator (same procedure as for theManifest). A representative URL is as follows:

http://translator.customer.com.akamaihd.net/custid1/metaindex/foo/bar/baz.mp4&format=mp4Forward IP/port: 127.0.0.1:yyyy

T→TG:

When the translator receives the request for the metaindex, it retrieves(via the stream cache process using same procedure as above for theManifest) a small subset of the original content, which the translatorHTTP proxy is able to retrieve from origin, preferably using partialobject caching (POC). For flv files, preferably only the very beginningand the last block will be read. For mp4/f4v files, preferably the“moov” atom at the beginning of the file is processed in its entirety. Acustomer-specific prefix and secret preferably are passed along thisentire path. A representative URL is as follows:

http://translator.customer.com.akamaihd.net/custid1/origin/foo/bar/baz.mp4

Forward IP/port: 127.0.0.1:80 TG→O:

The translator HTTP proxy ultimately goes forward to the appropriateorigin on POC misses. A representative URL is as follows:

URL: http://some.origin.com/some/customer/prefix/foo/bar/baz.mp4

EG→TG→O:

At this point, the edge machine HTTP proxy has a manifest and needs anindex. The edge machine HTTP proxy again goes forward to the translatorfor the index. The process proceeds in essentially the same way as forthe Manifest. For “mp4/f4v” files, preferably all indexes arepre-computed and stored verbatim in the metaindex so that no mp4/f4vcontent access is required. This is not a requirement, however. For“fly” files, producing full index information typically requires readingthe entire file; thus, for this type of content, preferably smallindexes (e.g., each a few seconds) are generated, e.g., using a binarysearch over the flv content and then downloading only that window ofcontent. The forward request from the HTTP proxy (as specified in theStream Manifest) may be as follows:

http://translator.customer.com.akamaihd.net/custid1/translate/foo/bar/baz.mp4?object=index&number=1234&etag=3-1234567890abAdditional query-string parameters may be passed from the manifest backto the index or fragment requests to ensure consistency between anyparameters that might have changed between manifest generation andindex/fragment retrieval.

EG→TG→ . . . →O:

The final type of request is for the actual fragment. For mp4/f4v files,the metaindex includes instructions sufficient to produce any requestedIF fragment without reparsing or otherwise consulting the original“moov” atom. Preferably, the actual raw data is retrieved via POC and/orthe stream cache process and assembled into valid IF fragments. For flvfiles, the fragment is generated by seeking directly to “desiredfragment size*(fragment number−1)” and then scanning forward for thefirst valid flv tag. The end of the fragment is just the first tagboundary at or after file offset “desired fragment size*(fragmentnumber)”. A representative URL is as follows:

http://translator.customer.com.akamaihd.net/custid1/translate/foo/bar/baz.mp4?object=fragment&number=1234&etag=3-1234567890ab

This completes the description of the client to origin request flow foran SBR stream request. The following provides additional detailsregarding the VOD implementation.

The metaindex is a binary format preferably comprising several sections,preferably in the following order: (i) fixed-size global header withper-stream information; (ii) additional “content-verifier” information,e.g., ETags, used to identify which file has been indexed; (iii) an“onMetaData” tag for the stream; (iv) per-track information, includingflv codec identifier and optional codec configuration parametersrequired by AAC and H.264; (v) (mp4/f4v only) Lookup table to mapfragment numbers to “sample_info” below; (vi) (mp4/f4v only) IF Indexes;(vii) (mp4/f4v only) “sample_info” which describes each individualsample to be interleaved into the output. The “sample_info” essentiallyis an optimized version of the “moov” atom that abstracts out many ofthe complexities of the mpeg-4 container. In general, this should be afairly compact representation, often smaller than the corresponding“moov” atom.

A Stream Manifest may include all bitrates of a multi-bit rate (MBR)stream. To produce an MBR Stream Manifest, the manifest request mayreference an SMIL file, which in turn contains the individual bitratesand flv or mp4/f4v source files. For MBR delivery, to produce the actualmanifest the translator downloads metaindexes for each bitrate. Theindex and fragment requests only require the metaindex file for theparticular bitrate(s) that the edge machine HTTP proxy wants to play.MBR fragment and index requests are similar to their SBR counterparts,except they also include an “smil= . . . ” query-string argument addedto each path in the C→EG→TG→T chain via patterns in a<locationlnfo> tagin the manifest.

Preferably, the actual format (“mp4” vs. “fly”) is included inmetaindex, fragment, and index URLs as a “format” query string argument.

As noted above, IF generation can take place within or in associationwith the HTTP proxy, including even an edge machine. This enables thecreation of content at the edge itself, close to the requesting enduser. Indeed, this approach (of IF generation in or in association withthe HTTP proxy) can move even further downstream, namely, into theclient machine itself. This is possible if the client includes softwarethat facilitates peer-based network session connectivity to apeer-to-peer (P2P) network, at least some portion of which is based onCDN resources including edge machines running HTTP proxies. As notedabove, it is possible the IF is generated in an HTTP proxy (or in aMuxer process associated therewith). When such P2P network sessionsoftware executes within a Client, it is possible to extend the HTTPproxy interface all the way downstream to the Client machine itself. Inthis approach, muxing takes place in the Client itself, in which casethe edge machine becomes just a “parent” cache in a cache-hierarchy thatincludes the client-side delivery mechanism. This approach could also beused with mobile devices with limited bandwidth.

The above-described approach provides numerous advantages. Thetechniques described herein facilitate the delivery of high definitionvideo and audio (including advanced video features, such as DVR) over anHTTP-edge network which, in a typical CDN, is the network that has thelargest footprint. By implementing the techniques, a provider canleverage its existing HTTP-based servers instead of having to implementand maintain dedicated server networks to support multiple third partyruntime environments. Moreover, because the delivery is HTTP-based, thecontent can be seamlessly delivered to clients operating across fixedline and mobile environments. No special client software is required, asthe HTTP proxy (that responds to the client request) dynamicallyre-assembles fragments that it obtains and serves the requested contentvia HTTP. Further, because delivery within the set of interconnectedmachines of the CDN preferably takes advantage of an intermediateformat, the network can ingest content in one format yet serve it inanother, all while preserving single or multi-bitrates and DVR-likefunctionality. Thus, for example, the network may take in live RTMPpackets and serve the content as an FLV progressive download.Preferably, each IF fragment of the stream is a separate object for theHTTP proxy that can be accessed, cached, and served via HTTP. Accordingto the scheme, the stream is broken up into many small objects(fragments), with each fragment managed separately.

The network is not limited for use with any particular runtimeenvironment such as Flash. By leveraging the approach as described, asingle set of content sources can be leveraged for different devicecapabilities. Thus, the techniques as described herein includedynamically transmuxing content to other file formats in a manner thatis transparent to the content provider and the end user.

The intermediate format may be based on or adapted from any convenientmultimedia file format that can be used delivery and playback ofmultimedia content. These include, without limitation, fragmented mp4,protected interoperable file format (piff), and others. More generally,any linked list-based file format may be used.

Preferably, the CDN service provider provides an extranet (a web-basedportal) through which the stream delivery is provisioned.

Each above-described process preferably is implemented in computersoftware as a set of program instructions executable in one or moreprocessors, as a special-purpose machine.

Representative machines on which the subject matter herein is providedmay be Intel Pentium-based computers running a Linux or Linux-variantoperating system and one or more applications to carry out the describedfunctionality. One or more of the processes described above areimplemented as computer programs, namely, as a set of computerinstructions, for performing the functionality described.

While the above describes a particular order of operations performed bycertain embodiments of the invention, it should be understood that suchorder is exemplary, as alternative embodiments may perform theoperations in a different order, combine certain operations, overlapcertain operations, or the like. References in the specification to agiven embodiment indicate that the embodiment described may include aparticular feature, structure, or characteristic, but every embodimentmay not necessarily include the particular feature, structure, orcharacteristic.

While the disclosed subject matter has been described in the context ofa method or process, the subject matter also relates to apparatus forperforming the operations herein. This apparatus may be a particularmachine that is specially constructed for the required purposes, or itmay comprise a computer otherwise selectively activated or reconfiguredby a computer program stored in the computer. Such a computer programmay be stored in a computer readable storage medium, such as, but is notlimited to, any type of disk including an optical disk, a CD-ROM, and amagnetic-optical disk, a read-only memory (ROM), a random access memory(RAM), a magnetic or optical card, or any type of media suitable forstoring electronic instructions, and each coupled to a computer systembus. A given implementation of the present invention is software writtenin a given programming language that runs in conjunction with aDNS-compliant name server (e.g., BIND) on a standard Intel hardwareplatform running an operating system such as Linux. The functionalitymay be built into the name server code, or it may be executed as anadjunct to that code. A machine implementing the techniques hereincomprises a processor, computer memory holding instructions that areexecuted by the processor to perform the above-described methods.

While given components of the system have been described separately, oneof ordinary skill will appreciate that some of the functions may becombined or shared in given instructions, program sequences, codeportions, and the like.

Having described the invention, what we claim is as follows:
 1. Acontent delivery system associated with an origin, comprising: a playertier; and a translation tier positioned intermediate the origin and theplayer tier, the translation tier comprising a network-accessiblemachine; the network-accessible machine comprising an HTTP proxy, and atranslator process that generates a manifest, an index and a set ofcontent fragments, wherein the HTTP proxy performs partial objectcaching (POC) and interacts with the translator process via a sharedmemory and using a stream cache process to selectively delivery to theplayer tier the manifest, the index and the set of content fragments.